The Mission Design and Navigation Software (MDN) Group at the Jet Propulsion Laboratory (JPL) develops and continuously maintains software systems critical for NASA deep space missions. Due to limited resources and tight schedules, there is always the temptation to prioritize productivity over quality. However, such quality and productivity variations may be manageable during development, but they are too risky for operational use when there is a time-critical need for repair or enhancement and high reliability is essential.As a result, our process must be both highly productive and maintain high quality (e.g., reliability, maintainability, usability). Inspired by the “quality is free” paradigm, we have instituted six policies established from DevOps principles and practices specifically to address maintenance risk caused by high variability in quality and productivity concerns we encountered in the development phase from quality-productivity tradeoffs.CMMI level 3 requirements mandate that process improvements are monitored and adjusted to ensure that policies are adhered to, practices are performed, and that they are effective in producing the desired results. This article presents a process improvement investigation as to whether the DevOps practices, as currently implemented, are effective in achieving the expected effects and impacts for managing variability in quality and productivity. Additionally, we investigate practical methods to assure compliance to the six policies to determine if any adjustments to policy or practice are needed.For this investigation we focus on our flagship system MONTE. We have over 15 years of reliable and accurate quality and productivity data for MONTE, a critical system currently in continual operation and maintenance. Time series cross-correlation analyses were used to compare process productivity and quality characteristics before and after the implementation of DevOps. From this, we found strong evidence that:• There is a continual maintenance risk due to variability in productivity and quality.• The majority of the DevOps policies and practices are being complied with.• The policies and practices have been effective in managing this risk.